Nashville PBS Design System · Handoff · October 23, 2026

What was done, what you do next, and how the pieces fit

Answers to every question from today, in order, plus the checklists and prompts you asked for. Facts about Claude products below were checked against Anthropic's help center today; where something is still rolling out, it says so.

1. Everything that changed in this project

Area	Change	Why
Brand artwork	Logos, Symbol Crop and both patterns embedded in the bundle (`brandAssetData.jsx`); patterns rebuilt as vectors (0.1% pixel difference). `Logo`, `PatternPanel`, `SymbolCrop`, `BrandAssets` no longer need files.	Consuming projects never receive `assets/`; this was the "broken logos" root cause.
Channel logos	14 official files imported from your `Channels` folder; two WORLD stacked files repaired (stripped fills); Create reverse built; `ChannelLogo`, `ChannelAssets`, `KidsArchitecture` components; "Channel Logos" card.	WORLD, Create, ALL ARTS, PBS KIDS were never in the system before today.
PBS KIDS rules	Station Logo Architecture 1.2.1 digested into SKILL.md and enforced by `KidsArchitecture` (never a lockup; beside/above the station logo; at least station-logo height; 25% clear space; optional "From/On" phrase).	From the PDF you supplied.
Rules	`SKILL.md` rewritten with hard rules, broadcast rules and trigger words; `readme.md` reconciled (Insight slates, no Curve on air, UHD 2×); `CLAUDE.md` reduced to a pointer.	Rules lived in a file consumers never read.
Tokens	Google Fonts import removed; weight 600 maps to Bold; top-right gradient tokens; 1240px content width.	Off-brand dependency, broken exports, missing broadcast angle.
On-Air template	Insight default, overlay toggle, % safe insets, 40px fit floor, notice / in-memoriam style, channel co-brand tweak (station / world / create / allarts / kids).	Matches station slates; Becky's memorial request.
New templates	Deck (16:9), Document (Letter), Social (1:1, 4:5, 9:16, 16:9), Flier (Letter).	Formats you reach for that had no artifact.
Repairs	Strategic Report and Brand Cover no longer point at files; image-slot drop zones replace pattern-as-photo.	Broken in consumers; patterns never go over imagery.
Hygiene	17 deprecated starting-point tags, stray logo PNGs and bad prompt examples removed; template loaders standardized.	Compiler: 0 issues, 33 cards, 8 templates, 32 components.
Deliverables	`audit/Design System Audit.html`, `samples/Samples Gallery.html`, this guide, `skill-package/nashville-pbs-design/` (org skill).

2. Downloads: which are valid

You were offered the skill zip three times as it grew. Only the last one in the chat (offered with this guide) is current. Everything else lives in this project and never needed downloading.

Trash"nashville-pbs-design skill (zip for your Team admin)" and "…(updated with channel logos)" and "…(Create reverse + PBS KIDS rules)" — superseded.
KeepThe download offered with this guide: nashville-pbs-design — contains SKILL.md, tokens, fonts, logos, patterns, channel logos, readme, PBS KIDS digest, INSTALL.md, CLAUDE.md snippet.
In projectAudit report, Samples Gallery, this guide, all templates and components. No download needed; they move with the design system.

3. How skills work (and whether someone has to "call" one)

Short answer: no, nobody has to call it, but it is probabilistic, not guaranteed.

A skill is a folder with a SKILL.md. Claude always sees every installed skill's name and description (about 100 tokens each). When a request matches a description, Claude loads the full SKILL.md on its own; supporting files (the readme, tokens) load only if it needs them. That is why I packed the description with your trigger words: Nashville PBS, WNPT, on-air, slate, endpage, lower third, pledge, Media Manager, PBS Blue. Anyone can also force it: in chat, "use the nashville-pbs-design skill"; in Claude Code, /nashville-pbs-design.

What a skill cannot do: it cannot stop Claude from ignoring a rule it did load. The two stronger mechanisms are (a) the design system binding in Claude, which injects tokens, components and templates deterministically into every design, and (b) templates whose props only allow legal values (one accent, fixed safe insets, approved backgrounds). Use all three layers.

4. Org settings: what you can program once for the whole Team

Default design system (Claude). After the re-move (section 6), an org Owner opens Settings > Design systems, opens the Nashville PBS menu and chooses Set as default. From then on every new design or deck anyone on the Team makes in Claude uses it without pulling anything in. Enterprise plans can also restrict who may publish or change the default.
Org-provisioned skill (Claude chat, Cowork, Code). An Owner goes to Organization settings > Plugins & skills > Add > Upload a skill and uploads the zip. It is enabled by default for every member and also syncs into Claude Code for people signed in with their Claude account. Prerequisite: in the Policy tab, "Cloud code execution and file creation" and "Skills" must be on. Only Owners (not Admins) can do this.
Claude Code managed instructions (IT). Managed settings can carry a claudeMd string that Claude Code loads ahead of every project's CLAUDE.md, on every machine your IT manages. Paste the brand block from CLAUDE.md.snippet there. Repos should still commit the skill to .claude/skills/nashville-pbs-design/.
Artifacts settings. Owners should confirm Artifacts and Design systems are on under Organization settings > Artifacts; the move depends on them.

5. Working with artifacts, projects and the generators

You are not using them wrong; one habit to change.

This project is the design system: tokens, components, templates, rules. Edit it only to change the brand or a generator. To make a screen or a graphic, start a new design (in Claude: Design tab > Make something new > Design). New designs pick up the published or default design system automatically and copy a template from the Templates picker when you ask for one. Prompting inside that new design never alters the design system. Prompting inside this project to make a one-off graphic does pollute the system, so avoid it.

The "graphics generators" you like (On-Air with its style, accent, channel and copy tweaks) are exactly the right pattern. In a consuming design: pick the On-Air template, open Tweaks, choose the style and fill the copy fields, drop the portrait or QR into the slot, turn on Safe guides, export at 2×. If you want a generator itself to change (a new style, a new rule), come back here, and every future design inherits it.

The Design tab in Claude, tile by tile

Design: a new design artifact (end cards, graphics, screens). It uses the default design system; ask for a template by name ("start from the On-Air Graphic template") and use Tweaks for style, accent, channel and copy.
Slides: Claude Slides. Pulls the design system's colors, type and logo for decks; exports to PowerPoint and PDF.
Design in codebase: design work inside a connected repository through Claude Code. This is where the skill folder and the CLAUDE.md snippet do their job.
Design System: creates a new design system. Do not use it to edit Nashville PBS; open the existing one from the grid and ask Claude for changes there.
Motion: animated pieces; the same design system applies.

6. Do you need to re-import into the new Claude Design? (corrected October 23)

Your design system already moved on October 20. The copy in Claude predates every fix made today.

Your Design tab shows "Nashville PBS Design System · Opened Oct 20" with the organization badge, and the banner reads "The latest move of your design systems finished." The broken logos and ignored rules came from that October 20 snapshot. Everything repaired today lives in the standalone source, so one more move carries it over.

Done: zips downloaded, brand-site/ and skill-package/ removed from the project.
In Claude's Design tab, click Move again in the banner. Per Anthropic's help center: a design system changed in the standalone app since the last move is moved; one unchanged in both places is marked "already moved"; one changed in Claude since the move is listed under Skipped so Claude-side edits are not overwritten.
Read the results. If Nashville PBS is under Moved, open it and confirm the Brand group shows the Channel Logos card and the template picker lists eight templates (On-Air, Deck, Document, Social, Flier, Strategic Report, Brand Cover, Media Manager). If it is under Skipped or "already moved": in Claude, open the design system, duplicate it only if someone made changes there you want to keep, delete it, then click Move again.
Do not click "Let Claude clean it up" on the moved copy. The system compiles with zero issues; a cleanup pass rewrites the guide and can soften the rules. If something looks wrong, ask Claude for that specific change.
Owner: Settings > Design systems > Nashville PBS > Set as default, and check it is shared with the organization so it appears in everyone's design system menu.
From then on, change the system in Claude by asking Claude inside it (it cannot be hand-edited there yet). Stop editing here: a system changed in Claude is skipped by later moves, and the standalone app closes December 14.

After the move, re-make the Lorenzo Washington end card from the On-Air template's notice style; it carries the title-safe insets, Insight background and white lockup automatically.

7. Test it: samples, and prompts for Chat and Code

Open samples/Samples Gallery.html. It renders all 8 templates (26 samples, including every On-Air style and channel co-brand) straight from the compiled bundle, with a pass/fail badge per sample for PBS Sans, images and bundle presence.

Claude chat (with the org skill provisioned, or the design system set as default)

Make a Nashville PBS on-air notice card, 1920x1080, for an in-memoriam message:
headline "Margaret Ann Whitfield", dates 1941–2026, visitation Saturday Nov 1, 2–4 p.m.,
Woodlawn Funeral Home, 660 Thompson Lane. Use the on-air template if available.
Before you finish, list how you satisfied: PBS Sans only, one accent, official logo untouched,
all text inside the inner 80% title-safe area, Insight pattern or navy background, no Curve.

Create a 6-slide Nashville PBS board update deck from these notes: [paste]. One accent color
for the whole deck, PBS Sans, Nashville PBS logo on every slide, section divider on the brand
pattern. Tell me which design-system templates and components you used.

Claude Code (repo with `.claude/skills/nashville-pbs-design/`)

/nashville-pbs-design Build a static HTML social graphic generator at /tools/social.html:
1080x1080, 1080x1350 and 1080x1920 frames, pattern/gradient/navy backgrounds, one accent
(teal/yellow/coral), headline + tune-in line, Nashville PBS or channel logo from the skill's
assets/, PBS Sans from the skill's fonts/. Add a "safe zones" toggle for stories.
Then run a self-check against SKILL.md's hard rules and print the results.

Negative test worth running: ask for "a Nashville PBS slate in Arial with a purple gradient" and confirm Claude refuses the font and the gradient and explains why.

8. Brand site like brand.github.com

Yes, and it should be generated from this design system, not written by hand.

brand.github.com is a public static guidelines site: Getting started, Brand identity (attributes, co-branding, voice), Foundations (logo, color, typography, accessibility), Graphic elements, Brand in action (presentations, social, web), Motion, with downloadable assets on each page. The Nashville PBS equivalent maps cleanly onto what already exists here: tokens → Color and Typography pages; Logo/ChannelLogo → Logo and Channels pages with downloads; patterns, Symbol Crop and graphic components → Graphic elements; SKILL.md → Rules, Voice and the broadcast page; templates → Brand in action.

Two decisions before I build it (form in the chat): whether it is public or internal, because PBS Sans is a licensed typeface and the PBS marks are PBS trademarks; a public site can show them but should not offer the font files for download, and logo downloads may need PBS's partner terms; and where it is hosted (GitHub Pages on a brand.wnpt.org subdomain is the brand.github.com model). I cannot create a GitHub repository from here; I will build the site as a folder in this project and hand Claude Code a one-paragraph instruction to create the repo, push it and enable Pages.

9. Your to-do list

YouDownload the final skill zip (below the guide in chat); delete the three earlier ones.
OwnerOrganization settings > Plugins & skills > Add > Upload a skill → the zip. Confirm it appears for a teammate under Customize > Skills.
DoneProject trimmed for the move (uploads archived offline; .bundles and skill-package removed; the skill zip and brand-site zip are your copies).
DoneZips downloaded (v4); brand-site/ and skill-package/ removed from the project. Regenerate both from this system when rules change.
YouClaude > Design tab > Move again. Check the result (section 6, step 3). If skipped or already moved: delete the Claude copy, then Move again.
OwnerSettings > Design systems > Nashville PBS > Set as default; confirm it is shared with the organization.
YouCreate a fresh design in Claude and run the two chat prompts above; compare against the Samples Gallery.
IT / CodeAdd the skill folder to .claude/skills/ in your repos and the CLAUDE.md snippet; optionally the managed claudeMd.
YouAnswer the brand-site form so I can build it; hand the Claude Code instruction to whoever owns your GitHub.

Claude Code is needed for exactly two things

Creating and publishing the brand-site repository (GitHub Pages), and dropping the skill + CLAUDE.md block into your code repos. Everything else in this guide happens in Claude settings or in this project.